|
|
|
|
|
|
Description: The name of the context currently facilitating the service processing the subscriber session.
|
|
|
|
Description: The identification number of the context currently facilitating the service processing the subscriber session. This is an internal reference number.
|
|
|
|
Description: The service name for which PDG statistics are being displayed.
|
|
|
|
Description: The service ID for which PDG statistics are being displayed.
|
|
|
|
Description: The bind IP address for this PDG service.
|
|
|
|
Description: System-wide PDG state identified by the following codes:
|
|
|
|
Description: Number of total current sessions.
|
|
|
|
Description: Number of currently active PDG sessions.
Trigger: Increments on receiving a new call request from the UE. For IPSec, it increments after receiving an IKE_INIT message from the UE. For SSL, it increments after the SSL tunnel is established.
|
|
|
|
Description: Number of currently dormant PDG sessions.
Trigger: For SSL, it represents those subscribers wherein the TCP connection is up but the SSL tunnel is not yet up.
|
|
|
|
Description: Number of currently active IPv4 sessions.
|
|
|
|
Description: Number of currently dormant IPv4 sessions.
|
|
|
|
Description: Number of currently active IPv6 sessions.
|
|
|
|
Description: Number of currently dormant IPv6 sessions.
|
|
|
|
Description: Number of current direct IP IPv4 sessions.
|
|
|
|
Description: Number of current TTG IPv4 sessions.
|
|
|
|
Description: Total number of direct IP IPv4 sessions.
Trigger: Increments upon successful IPv4 PDG mode call setup.
|
|
|
|
Description: Total number of TTG IPv4 sessions.
Trigger: Increments upon successful IPv4 TTG mode call setup.
|
|
|
|
Description: Number of direct IP IPv4 successful sessions.
Trigger: Increments upon successful IPv4 PDG mode call setup.
|
|
|
|
Description: Number of direct IP IPv4 attempted sessions.
Trigger: Increments upon receiving an IKE_INIT message from the UE in IPsec and a TCP SYN message from the UE in SSL.
|
|
|
|
Description: Number of direct IP IPv4 attempted sessions that failed.
Trigger: Increments upon a session setup timeout and authentication failure scenario in PDG mode IPv4 call setup.
|
|
|
|
Description: Number of direct TTG IPv4 successful sessions.
Trigger: Increments upon a successful IPv4 TTG mode call setup.
|
|
|
|
Description: Number of direct TTG IPv4 attempted sessions.
Trigger: Increments upon receiving an IKE_INIT message from the UE in IPsec and a TCP SYN message from the UE in SSL TTG mode.
|
|
|
|
Description: Number of direct TTG IPv4 attempted sessions that failed.
Trigger: Increments upon a session setup timeout and authentication failure scenario in PDG mode IPv4 call setup.
|
|
|
|
Description: Total number of sessions set up.
Trigger: Increments upon sending a successful IKE_AUTH CFG response to the UE in IPSec, and upon a successful call setup with an MT_CLOSE message sent to the UE in SSL.
|
|
|
|
Description: Total number of session attempted.
Trigger: Increments upon receiving an IKE_INIT message from the UE in IPsec and a TCP SYN message in SSL TTG mode.
|
|
|
|
Description: Total number of session attempts failed.
Trigger: Increments upon session setup timout and authentication failure scenario or a resource unavailable scenario where the subscriber allocation fails.
|
|
|
|
Description: Total number of sessions disconnected.
Trigger: Increments after call is up during re-authentication failure (IPSec only) and the SSL or IPSec tunnel goes down.
|
|
|
|
Description: Total number of sessions disconnected locally.
Trigger: Increments by unavailable resources and session setup timeout.
|
|
|
|
Description: Total number of sessions disconnected remotely.
Trigger: Increments on UE-initiated call tear down after call setup.
|
|
|
|
Description: Sessions remotely disconnected before connected.
Trigger: Increments on UE-initiated call tear down before call setup.
|
|
|
|
Description: Total fast re-authentication successes.
Trigger: Increments upon re-authetication success scenario. Includes both fast re-authentication and pseudoname re-authentication.
|
|
|
|
Description: Total fast re-authentication attempts.
Trigger: Increments upon receiving the re-auth ID in the IKE-AUTH message from the UE. Includes both fast re-authentication and pseudoname re-authentication.
|
|
|
|
Description: Total fast re-authentication attempts that failed.
Trigger: Increments upon a re-authentication success scenario from the AAA server. Includes both fast re-authentication and pseudoname re-authentication.
|
|
|
|
Description: Total reauthorization attempts that succeeded.
Trigger: Increments upon receiving an authorize success message from the AAA server.
|
|
|
|
Description: Total reauthorization attempts.
Trigger: Increments upon sending an authorize request message to the AAA server.
|
|
|
|
Description: Total reauthorization attempts that failed.
Trigger: Increments upon an authorization failure with the AAA server or if the IPsec tunnel goes down during authorization.
|
|
|
|
Description: Total primary AAA sessions that succeeded.
Trigger: Increments upon receiving an access accept message from the AAA server. (Increments only during primary authentication if multiple authentication is supported in IPSec).
|
|
|
|
Description: Total primary AAA sessions attempted.
Trigger: Increments upon receiving an IKE -AUTH message from the UE in IPSec and an MT-AUTH message from the UE in SSL.
|
|
|
|
Description: Total primary AAA sessions that failed.
Trigger: Increments on an authentication failure and if the SSL or IPSec tunnel goes down during authentication.
|
|
|
|
Description: Total external AAA sessions that succeeded.
Trigger: Increments upon receiving an authentication success message from the AAA server in a multiple authentication scenario.
|
|
|
|
Description: Total external AAA sessions that attempted.
Trigger: Increments upon receiving an IKE-AUTH (ANOTHER-AUTH-FOLLOWS) message from the UE in a multiple authentication scenario.
|
|
|
|
Description: Total external AAA sessions that failed.
Trigger: Increments upon receiving an authentication failure from the AAA server or an IPsec tunnel tear down in a multiple authentication scenario.
|
|
|
|
Description: Total of successful EAP authorizations.
Trigger: Increments upon receiving an authentication success message from the AAA server for the second phase authentication using EAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Total of failed EAP authorizations.
Trigger: Increments upon receiving an authentication failure message from the AAA server for the second phase authentication using EAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Total of successful PAP authorizations.
Trigger: Increments upon receiving an authentication success message from the AAA server for the second phase authentication using PAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Total of failed PAP authorizations.
Trigger: Increments upon receiving an authentication failure message from the AAA server for the second phase authentication using PAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Total of successful CHAP authorizations.
Trigger: Increments upon receiving an authentication success message from the AAA server for the second phase authentication using CHAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Total of failed CHAP authorizations.
Trigger: Increments upon receiving an authentication failure message from the AAA server for the second phase authentication using CHAP. (Applicable only in a multiple authentication scenario.)
|
|
|
|
Description: Number of sessions terminated by a remote disconnect.
Trigger: A TCP failure scenario in SSL PDG and SSL TTG after the call is in the CONNECTED state. A UE-initiated session disconnect in IPSec PDG and IPSec TTG after the call is in the CONNECTED state.
|
|
|
|
Description: Number of sessions terminated by a Session Attempt Failed disconnect reason due to a remote disconnect.
Trigger: A TCP failure scenario in SSL PDG and SSL TTG before the call is in the CONNECTED state. A UE-initiated session disconnect in IPSec PDG and IPSec TTG before the call is in the CONNECTED state.
|
|
|
|
Description: Number of sessions terminated because of an admin release.
Trigger: Incremented for all sessions in a CONNECTED state that are cleared due to an Admin Disconnect disconnect reason.
|
|
|
|
Description: Number of sessions terminated by a Session Attempt Failed disconnect reason due to an admin disconnect.
Trigger: Incremented for all session setups that failed due to an admin disconnect before the session is in a CONNECTED state.
|
|
|
|
Description: Number of sessions terminated because of idle timer timeout.
|
|
|
|
Description: Number of sessions terminated because of absolute timeout.
|
|
|
|
Description: Number of sessions terminated because of long duration timer timeout.
|
|
|
|
Description: Number of sessions terminated because of Session Manager session setup timeout.
|
|
|
|
Description: Number of sessions terminated because of non-existence of PCRF.
|
|
|
|
Description: Number of sessions terminated because of no resources.
|
|
|
|
Description: Number of sessions terminated because of AAA authentication failure.
Trigger: Incremented on receiving an Access-Reject message, an invalid AAA attribute in an Access-Accept message, an AAA timeout message, a missing AAA attribute in an Access-Accept message, an invalid W-APN format, or an invalid NAI format. Also incremented in PDG mode if W-APN is not configured.
|
|
|
|
Description: Number of sessions terminated because of a session re-authetication failure.
Trigger: Incremented for all AAA failures during fast re-authentication or pseudonym re-authentication.
|
|
|
|
Description: Number of sessions terminated because of flow add failure.
|
|
|
|
Description: Number of sessions terminated because of invalid destination context.
|
|
|
|
Description: Number of sessions terminated because of source IP address violation.
|
|
|
|
Description: Number of sessions terminated because of a GTP failure.
Trigger: Incremented for all GTP path failures or DPC requests from the GGSN.
Availability: IPSec/SSL (TTG only).
|
|
|
|
Description: Number of session attempts failed because of GTP failure.
Trigger: Incremented for all session setups failed due to CPC failure/timeout.
Availability: IPSec/SSL (TTG only).
|
|
|
|
Description: Number of sessions terminated because of duplicate requests.
Trigger: Incremented on receiving a new call when a previous call exists in the CONNECTED state with the same IMSI and APN on the same Session Manager. When this occurs, the original call is cleared.
Availability: IPSec/SSL (TTG only).
|
|
|
|
Description: Number of session attempts failed because of duplicate requests.
Trigger: Incremented on receiving a new call when a previous call exists in the CONNECTED state with the same IMSI and APN on the same Session Manager. When this occurs, the original call is cleared.
Availability: IPSec/SSL (TTG only).
|
|
|
|
Description: Number of sessions terminated because of an address assignment failure.
|
|
|
|
Description: Number of sessions terminated because of miscellaneous reasons.
Trigger: Incremented for all SSL failures and all remaining disconnect reasons (for example, for IPSec, no-response or remote-error-notification).
|
|
|
|
Description: Number of session attempts failed because of miscellaneous reasons.
Trigger: Incremented for all session setup failures due to SSL failures (for example, handshake failures, ssl-alert, ssl-bad-message), or an unknown APN case in which the TTG is unable to resolve the APN and all remaining disconnect reasons before the call is in the CONNECTED state.
|
|
|
|
Description: Total number of bytes sent.
|
|
|
|
Description: Total number of bytes received.
|
|
|
|
Description: Total number of packets sent.
|
|
|
|
Description: Total number of packets received.
|
|
|
|
Description: Total number of packet violations.
|
|
|
|
Description: Total number of EAP messages received from the EAP server in pass-through mode.
|
|
|
|
Description: Total number of EAP-Success messages received from the EAP server in pass-through mode.
|
|
|
|
Description: Total number of EAP-Failure messages received from the EAP server in pass-through mode.
|
|
|
|
Description: Total number of EAP challenge messages sent to the EAP server in pass-through mode.
|
|
|
|
Description: Total number of EAP messages transmitted to the EAP server.
|
|
|
|
Description: Total number of EAP request messages forwarded to the EAP server for initial request.
|
|
|
|
Description: Total number of EAP messages transmitted to the EAP server for forward request.
|
|
|
|
Description: Total number of EAP messages transmitted to the EAP server in pass-through mode for mobile node.
|
|
|
|
Description: Total number of EAP messages transmitted to the EAP server that were discarded.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes sent.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped due to non-connected state.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped due to transport stack buffer over flow.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped due to incorrect destination IP address.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped due to transport stack failed to send.
|
|
|
|
Description: SSL micro-tunneling: Uplink data bytes dropped due to session not found for sock-id.
|
|
|
|
Description: SSL micro-tunneling: Downlink data bytes sent.
|
|
|
|
Description: SSL micro-tunneling: Total OPEN requests received.
|
|
|
|
Description: SSL micro-tunneling: OPEN requests processed.
|
|
|
|
Description: SSL micro-tunneling: OPEN requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total OPEN responses sent.
|
|
|
|
Description: SSL micro-tunneling: OPEN responses accepted.
|
|
|
|
Description: SSL micro-tunneling: OPEN responses rejected.
|
|
|
|
Description: SSL micro-tunneling: OPEN responses received.
|
|
|
|
Description: SSL micro-tunneling: Total NAM requests received.
|
|
|
|
Description: SSL micro-tunneling: NAM requests processed.
|
|
|
|
Description: SSL micro-tunneling: NAM requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total NAM responses sent.
|
|
|
|
Description: SSL micro-tunneling: NAM responses accepted.
|
|
|
|
Description: SSL micro-tunneling: NAM responses rejected.
|
|
|
|
Description: SSL micro-tunneling: NAM responses received.
|
|
|
|
Description: SSL micro-tunneling: Total AUTH requests received.
|
|
|
|
Description: SSL micro-tunneling: AUTH requests processed.
|
|
|
|
Description: SSL micro-tunneling: AUTH requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total AUTH responses sent.
|
|
|
|
Description: SSL micro-tunneling: AUTH responses accepted.
|
|
|
|
Description: SSL micro-tunneling: AUTH responses rejected.
|
|
|
|
Description: SSL micro-tunneling: AUTH responses received.
|
|
|
|
Description: SSL micro-tunneling: Total RECV requests received.
|
|
|
|
Description: SSL micro-tunneling: RECV requests processed.
|
|
|
|
Description: SSL micro-tunneling: RECV requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total RECV responses sent.
|
|
|
|
Description: SSL micro-tunneling: RECV responses accepted.
|
|
|
|
Description: SSL micro-tunneling: RECV responses rejected.
|
|
|
|
Description: SSL micro-tunneling: RECV responses received.
|
|
|
|
Description: SSL micro-tunneling: Total CLOSE requests received.
|
|
|
|
Description: SSL micro-tunneling: CLOSE requests processed.
|
|
|
|
Description: SSL micro-tunneling: CLOSE requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total CLOSE requests sent.
|
|
|
|
Description: SSL micro-tunneling: CLOSE requests dispatched.
|
|
|
|
Description: SSL micro-tunneling: Total CLOSE responses received.
|
|
|
|
Description: SSL micro-tunneling: CLOSE responses accepted.
|
|
|
|
Description: SSL micro-tunneling: CLOSE responses rejected.
|
|
|
|
Description: SSL micro-tunneling: CLOSE responses dropped.
|
|
|
|
Description: SSL micro-tunneling: Total CLOSE responses sent.
|
|
|
|
Description: SSL micro-tunneling: CLOSE responses accepted.
|
|
|
|
Description: SSL micro-tunneling: CLOSE responses rejected.
|
|
|
|
Description: SSL micro-tunneling: Total SEND requests received.
|
|
|
|
Description: SSL micro-tunneling: SEND requests processed.
|
|
|
|
Description: SSL micro-tunneling: SEND requests dropped.
|
|
|
|
Description: SSL micro-tunneling: Total SEND requests sent.
|
|
|
|
Description: SSL micro-tunneling: SEND requests dispatched.
|
|
|
|
Description: SSL micro-tunneling: Total SEND responses received.
|
|
|
|
Description: SSL micro-tunneling: SEND responses accepted.
|
|
|
|
Description: SSL micro-tunneling: SEND responses rejected.
|
|
|
|
Description: SSL micro-tunneling: SEND responses dropped.
|
|
|
|
Description: SSL micro-tunneling: Total SEND responses sent.
|
|
|
|
Description: SSL micro-tunneling: SEND responses accepted.
|
|
|
|
Description: SSL micro-tunneling: SEND responses rejected.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: cannot create connection.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: protocol not supported.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: permission denied.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: cannot create sock-id.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: address or port already used.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: cannot connect the server.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: hostname is unknown.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: authentication required.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: version not supported.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: server cannot create an authentication process.
|
|
|
|
Description: SSL micro-tunneling: OPEN Reject sent: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: NAM Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: NAM Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: AUTH Reject sent: the auth-id is unknown.
|
|
|
|
Description: SSL micro-tunneling: AUTH Reject sent: cannot connect to authentication server.
|
|
|
|
Description: SSL micro-tunneling: AUTH Reject sent: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: AUTH Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: AUTH Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: the sock-id is unknown.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: the connection is lost.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: permission denied.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: RECV Reject sent: the sock-id is unknown.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject sent: the connection is lost.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject sent: the bad parameters.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject received: sock-id unknown.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject received: the connection is lost.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject received: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject received: undefined.
|
|
|
|
Description: SSL micro-tunneling: CLOSE Reject received: reserved.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: sock-id unknown.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: the connection is lost.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: permission denied.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: undefined.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject sent: reserved.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: sock-id unknown.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: connection is lost.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: permission denied.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: bad parameters.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: undefined.
|
|
|
|
Description: SSL micro-tunneling: SEND Reject received: reserved.
|
|
|
|
Description: SSL micro-tunneling: Packets discarded statistics: unknown version.
|
|
|
|
Description: SSL micro-tunneling: Packets discarded statistics: unknown message type.
|
|
|
|
Description: SSL micro-tunneling: Packets discarded statistics: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Packets discarded statistics: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: OPEN: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: OPEN: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP OPEN: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP OPEN: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: CLOSE: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: CLOSE: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: CLOSE: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: CLOSE: unknown context, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP CLOSE: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP CLOSE: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: NAM: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: NAM: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: NAM: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: NAM: unknown context, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP NAM: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP NAM: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: AUTH: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: AUTH: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: AUTH: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: AUTH: unknown context, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP AUTH: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP AUTH: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RECV: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RECV: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RECV: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RECV: unknown context, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP RECV: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP RECV: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: SEND: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: SEND: decoding failed, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: SEND: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: SEND: unknown context, rejected.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP SEND: decoding failed, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP SEND: unknown context, dropped.
|
|
|
|
Description: SSL micro-tunneling: Messages denied statistics: RESP to unknown command dropped.
|
|
Important: See the “Bulk Statistics Overview” chapter for statistics that are common to all schema.
|